Hans, Wolfgang,
I am so happy to receive your immediate answers. — Thanks a lot, the problem is
solved and I get the colored labeltext!
Thank you
Willi
> On 24 Jun 2022, at 19:19, Hans Hagen via ntg-context
> wrote:
>
> On 6/24/2022 4:34 PM, Willi Egger via ntg-context wrot
On 6/24/2022 4:34 PM, Willi Egger via ntg-context wrote:
Hi all,
Sorry for bothering you again.
I would like that lua is returning a colored string, which is a label-text.
The following does not work, the labeltext remains black, there is no error
though:
return context.color({&quo
Willi Egger via ntg-context schrieb am 24.06.2022 um 16:34:
Hi all,
Sorry for bothering you again.
I would like that lua is returning a colored string, which is a label-text.
The following does not work, the labeltext remains black, there is no error
though:
return context.color({&quo
Hi all,
Sorry for bothering you again.
I would like that lua is returning a colored string, which is a label-text.
The following does not work, the labeltext remains black, there is no error
though:
return context.color({"red"},context.labeltext(s))
What is the correct approac
Thank you very much Wolfgang for the explanation,
Both solutions make sense now and work great.
Regards,
Adam
On Wed, Aug 25, 2021 at 11:46 AM Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:
> Adam Reviczky via ntg-context schrieb am 25.08.2021 um 02:02:
> > Hi,
> >
> > I have
Adam Reviczky via ntg-context schrieb am 25.08.2021 um 02:02:
Hi,
I have asked this question before, but now I cannot get it working again.
https://ntg-context.ntg.narkive.com/lvvdNOQz/the-appendices-envrionment-and-title-in-toc
I want to set partlabels in my TOC but not in the document
Hi,
I have asked this question before, but now I cannot get it working again.
https://ntg-context.ntg.narkive.com/lvvdNOQz/the-appendices-envrionment-and-title-in-toc
I want to set partlabels in my TOC but not in the document itself.
The desired output would be:
---
Contents
Chapter 1 Bodypart
:
\setuplabeltext[en][test=Something]
\startluacode
context.startsectionlevel{title="\\labeltext[test]"}
-- ...
context.stopsectionlevel()
\stopluacode
The title correctly reads "Something", but the bookmark in the PDF
viewer shows "test".
also
be a crossover between lua and
tex, but that results in the bookmark having the wrong label:
\setuplabeltext[en][test=Something]
\startluacode
context.startsectionlevel{title="\\labeltext[test]"}
-- ...
context.stopsectionlevel()
\stopluacode
The title correctly reads "Something&quo
, but that results in the bookmark having the wrong label:
\setuplabeltext[en][test=Something]
\startluacode
context.startsectionlevel{title="\\labeltext[test]"}
-- ...
context.stopsectionlevel()
\stopluacode
The title correctly reads "Something", but the bookmark in the PDF
viewer shows &qu
On 2/16/2017 2:12 PM, Andreas Schneider wrote:
Am 2017-02-16 11:50, schrieb Hans Hagen:
languages.data.labels.texts.appendix.labels.en
look into lang-txt.lua
Hello Hans,
I already looked into this and even printed the whole languages.data
table at runtime, but didn't find my keys in there.
Am 2017-02-16 11:50, schrieb Hans Hagen:
languages.data.labels.texts.appendix.labels.en
look into lang-txt.lua
Hello Hans,
I already looked into this and even printed the whole languages.data
table at runtime, but didn't find my keys in there.
Here is an example which apparently doesn't
On 2/16/2017 11:36 AM, Andreas Schneider wrote:
Hello,
if I define a labeltext via \setuplabeltext[en][test=Something], how can
I access that value via lua?
(context.labeltext obviously prints the content, but doesn't allow me to
use it in lua).
languages.data.labels.texts.appendix.labels.en
Hello,
if I define a labeltext via \setuplabeltext[en][test=Something], how can
I access that value via lua?
(context.labeltext obviously prints the content, but doesn't allow me to
use it in lua).
As a related side-request: how can I fix expansion in cases like this:
\startsectionlevel
On 16-6-2012 15:19, Philipp Gesang wrote:
Hi Hans!
···date: 2012-06-12, Tuesday···from: Hans Hagen···
On 12-6-2012 16:41, Philipp Gesang wrote:
I’ll be collecting candidates for the wiki page until saturday
and then write up a draft, maybe submit it to the list for review
first. I can draw
Hi Hans!
···date: 2012-06-12, Tuesday···from: Hans Hagen···
On 12-6-2012 16:41, Philipp Gesang wrote:
I’ll be collecting candidates for the wiki page until saturday
and then write up a draft, maybe submit it to the list for review
first. I can draw up a preliminary list first so you can
Am 12.06.2012 um 00:22 schrieb Aditya Mahajan:
On Mon, 11 Jun 2012, Aditya Mahajan wrote:
On Mon, 11 Jun 2012, Philipp Gesang wrote:
Dear others, please contribute if you know about further setups
whose parameters behave in a non-standard way. As this is quite
counterintuitive, I’d like
On 2012-06-11 Philipp Gesang ges...@stud.uni-heidelberg.de wrote:
Dear others, please contribute if you know about further setups
whose parameters behave in a non-standard way.
Here's another candidate: \usepath
http://article.gmane.org/gmane.comp.tex.context/75727
As this is quite
On 12-6-2012 13:42, Marco wrote:
On 2012-06-11 Philipp Gesang ges...@stud.uni-heidelberg.de wrote:
Dear others, please contribute if you know about further setups
whose parameters behave in a non-standard way.
Here's another candidate: \usepath
On 2012-06-12 Hans Hagen pra...@wxs.nl wrote:
On 12-6-2012 13:42, Marco wrote:
On 2012-06-11 Philipp Gesang ges...@stud.uni-heidelberg.de wrote:
Dear others, please contribute if you know about further setups
whose parameters behave in a non-standard way.
Here's another candidate:
On 12-6-2012 16:24, Marco wrote:
While you're at it, check \usesubpath as well. I didn't test, but
assume it has the same issue.
uses the same code
As this is quite counterintuitive, I’d like to wikify any known
exceptions somewhere over here:
How about unifying the interface? IMO that
Hi Hans!
···date: 2012-06-12, Tuesday···from: Hans Hagen···
On 12-6-2012 16:24, Marco wrote:
While you're at it, check \usesubpath as well. I didn't test, but
assume it has the same issue.
uses the same code
As this is quite counterintuitive, I’d like to wikify any known
exceptions
On 12-6-2012 16:41, Philipp Gesang wrote:
I’ll be collecting candidates for the wiki page until saturday
and then write up a draft, maybe submit it to the list for review
first. I can draw up a preliminary list first so you can have a
look at it.
next week is ok
Hans
Hi all,
there appears to be something special about how the key-value
list works with \setuplabeltext:
···
\setuplabeltext [
foo=bar, %% - comma not allowed here?
% foo=bar %% - works
]
\starttext
\labeltext{foo
%% - works
]
\starttext
\labeltext{foo}
\stoptext
···
Normally the trailing comma causes no trouble, but here it won’t
even compile.
indeed a slightly different parser is used here
:
···
\setuplabeltext [
foo=bar, %% - comma not allowed here?
% foo=bar %% - works
]
\starttext
\labeltext{foo}
\stoptext
···
Normally the trailing comma causes no trouble, but here it won’t
even compile
:
···
\setuplabeltext [
foo=bar, %% - comma not allowed here?
% foo=bar %% - works
]
\starttext
\labeltext{foo}
\stoptext
···
Normally the trailing comma causes no trouble
how the key-value
list works with \setuplabeltext:
···
\setuplabeltext [
foo=bar, %% - comma not allowed here?
% foo=bar %% - works
]
\starttext
\labeltext{foo}
\stoptext
On Mon, 11 Jun 2012, Philipp Gesang wrote:
Dear others, please contribute if you know about further setups
whose parameters behave in a non-standard way. As this is quite
counterintuitive, I’d like to wikify any known exceptions
somewhere over here:
On Mon, 11 Jun 2012, Aditya Mahajan wrote:
On Mon, 11 Jun 2012, Philipp Gesang wrote:
Dear others, please contribute if you know about further setups
whose parameters behave in a non-standard way. As this is quite
counterintuitive, I’d like to wikify any known exceptions
somewhere over here:
Hi Aditya!
···date: 2012-06-11, Monday···from: Aditya Mahajan···
On Mon, 11 Jun 2012, Philipp Gesang wrote:
Dear others, please contribute if you know about further setups
whose parameters behave in a non-standard way. As this is quite
counterintuitive, I’d like to wikify any known
Hi Aditya!
···date: 2012-06-11, Monday···from: Aditya Mahajan···
On Mon, 11 Jun 2012, Aditya Mahajan wrote:
On Mon, 11 Jun 2012, Philipp Gesang wrote:
Other potential topics that fit better on such a page:
* Why is space after \externalfigure[..][..] gobbled? (in the FAQ)
* Why does
On Mon, Oct 24, 2011 at 20:41, Hans Hagen pra...@wxs.nl wrote:
On 24-10-2011 19:41, Mojca Miklavec wrote:
Hello,
The following code
\setuplabeltext[test=]
test is \doifemptyelse{\labeltext{test}}{empty}{not empty}
doesn't work as intended for the reasons that I approximately
understand
On 25-10-2011 11:26, Mojca Miklavec wrote:
On Mon, Oct 24, 2011 at 20:41, Hans Hagenpra...@wxs.nl wrote:
On 24-10-2011 19:41, Mojca Miklavec wrote:
Hello,
The following code
\setuplabeltext[test=]
test is \doifemptyelse{\labeltext{test}}{empty}{not empty}
doesn't work as intended
On Tue, 25 Oct 2011, Mojca Miklavec wrote:
you can try \doiftextelse instead
Thank you very much. This works fine.
This should probably be added to
http://wiki.contextgarden.net/System_Macros/Branches_and_Decisions
at least (possibly to reference next to labels as well), but I'm not
sure
Hello,
The following code
\setuplabeltext[test=]
test is \doifemptyelse{\labeltext{test}}{empty}{not empty}
doesn't work as intended for the reasons that I approximately
understand (not exactly, but I understand that there might be a lot of
weird stuff returned when I ask for labeltext
On 24-10-2011 19:41, Mojca Miklavec wrote:
Hello,
The following code
\setuplabeltext[test=]
test is \doifemptyelse{\labeltext{test}}{empty}{not empty}
doesn't work as intended for the reasons that I approximately
understand (not exactly, but I understand that there might be a lot of
weird
37 matches
Mail list logo
